Twitter, the bus
The real power of Twitter is that with its viral spread it may provide an excellent delivery mechanism for meaningful information that will enable the next generation of services. Of course the hype is in posting meaningless tidbits of life that have little value to anyone but the poster and a few close friends, but nonetheless widespread adoption is an important step for the next phase to become feasible.
Steve Rubel asked how people are using Twitter and from his post it seems most people perceive it as a micro-blogging platform. But imagine the following evolution of this service:
- Web applications start to report state of their users to Twitter via its API. Although authentication is required, many web application could built in this information into the user profile, making it transparent during the session.
- A simple tag microformat built into Twitter evolves as the de-facto standard to organize this neverending stream of data.
- Twitter itself or some other provider will implement a service for aggregating Twitter feeds that share the same tags, allowing subscribers to subscribe to the RSS of specific events
- A particular subscriber will sniff all these posts and react when a particular "event" is triggered
This breakdown is a bit abstract, but the paradigm of even-driven programming may provide a better idea for those familiar with it. With Twitter you should be able to build applications that react to events triggered by people.
A couple of years ago I wrote the Birth of Cool. While at the time I was convinced that a certain electronic device would be at the core of such scenario, the basic premise works with Twitter. The binary breadcrumb is left behind allowing anyone to build up interesting services around it.
Now imagine a service that warns you every time you're about to purchase an item that exists elsewhere at a discounted price. Or being offered a discount in a good restaurant when you land into another city.
Update: Michael Parekh, Tara Hunt and Kathy Sierra have their own opinions about how to best leverage (or not) Twitter, but I'm surprised using it as an event trigger (as in event-driven architectures) is not one of them yet.
Labels: rss, subscribers, twitter





